Bump gitpython from 3.1.57 to 3.1.58 - #779
Merged
Merged
Conversation
dependabot
Bot
added
dependencies
n-shevko
force-pushed
the
dependabot/pip/gitpython-3.1.58
branch
from
August 29, 2026 18:25
c3156a6 to
9cb1eab
Compare
Hananel-Hazan
added a commit
that referenced
this pull request
Sep 2, 2026
…CURITY.md (#784) * docs: add SECURITY.md with reporting process and incident note * deps: upgrade all dependencies, closing 12 Dependabot security alerts Closes all 12 open Dependabot alerts (7 high, 3 moderate, 2 low): gitpython 3.1.57 -> 3.1.61 (6 alerts: 5 high, 1 moderate) tornado 6.5.7 -> 6.5.8 (3 alerts: 1 high, 1 moderate, 1 low) mistune 3.3.0 -> 3.3.4 (1 high) setuptools 81.0.0 -> 84.0.0 (1 moderate) torch 2.11.0 -> 2.14.0 (1 low) The gitpython alerts had stayed open even though PR #779 claimed to bump it to 3.1.58. That branch had been force-pushed to the malicious commit 9cb1eab, so merging it delivered malware instead of the dependency fix (see #781). Two changes were needed to move torch at all: - The CUDA wheel index moves from cu128 to cu130. The cu128 index stops at torch 2.11.0, so the vulnerable version could not be fixed on it. This raises the NVIDIA driver requirement for users installing the GPU build. - torchaudio is removed. Its newest release anywhere is 2.11.0 and it pins torch==2.11.0, so it blocks every torch upgrade. Nothing in BindsNET imports it; 'grep -rn torchaudio --include=*.py' returns no matches. The rest of the lock file is a full re-resolve to current versions. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Hananel-Hazan
added a commit
that referenced
this pull request
Sep 2, 2026
Until now only Dependabot security updates ran on this repository. That is why poetry.lock drifted far enough to accumulate 12 open security alerts before anyone noticed, six of which were a single GitPython advisory left unfixed since PR #779 failed to deliver the bump (see #781). Two ecosystems, both weekly: pip minor and patch bumps arrive as one grouped pull request so routine maintenance is a single review. Major bumps stay separate. github-actions action versions are their own supply chain surface; a compromised action runs with access to the workflow. torch and torchvision are excluded from version updates. They are pinned to exact versions from the custom CUDA wheel index in pyproject.toml and have to move together, so routine bumps would break the pairing or pull the plain PyPI build instead. The exclusions are scoped to version-update types only, so security alerts for torch and torchvision still come through. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps gitpython from 3.1.57 to 3.1.58.
Release notes
Sourced from gitpython's releases.
Commits
30be45dprepare changelog for upcoming releasefc2f02cMerge pull request #2197 from Cyrus580529/shared-symlink-guardb10e250test: use the shared guard instead of local copiese3e5da8test: skip tests that need symlink privileges30d05e3test: add a shared symlink capability guard9a8f6feMerge pull request #2204 from gitpython-developers/security-fixesf2550b6Guard pathspec file inputs in high-level commandsd9ddb55Guard unsafe git init options9b5dcafGuard read-tree index output paths96a888fCheck joined short-option values before Git executionDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.